-
Notifications
You must be signed in to change notification settings - Fork 289
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ADD] PyTorch embedding layer to reduce memory footprint #451
Open
ravinkohli
wants to merge
22
commits into
reg_cocktails
Choose a base branch
from
reg_cocktails-pytorch_embedding
base: reg_cocktails
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ravinkohli
commented
Jul 18, 2022
autoPyTorch/api/base_task.py
Outdated
@@ -249,6 +249,7 @@ def __init__( | |||
|
|||
self.input_validator: Optional[BaseInputValidator] = None | |||
|
|||
# if search_space_updates is not None else get_search_updates(categorical_indicator) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Suggested change
# if search_space_updates is not None else get_search_updates(categorical_indicator) |
ravinkohli
force-pushed
the
reg_cocktails
branch
from
July 26, 2022 13:43
738be75
to
c138173
Compare
ravinkohli
changed the title
Reg cocktails pytorch embedding
[ADD] PyTorch embedding layer to reduce memory footprint
Aug 9, 2022
1 task
ravinkohli
force-pushed
the
reg_cocktails-pytorch_embedding
branch
from
August 16, 2022 15:22
3761b53
to
d4717fb
Compare
* remove remaining differences * Reg cocktails common paper modifications 5 (#418) * add hasttr * fix run summary
…edding) (#437) * add updates for apt1.0+reg_cocktails * debug loggers for checking data and network memory usage * add support for pandas, test for data passing, remove debug loggers * remove unwanted changes * : * Adjust formula to account for embedding columns * Apply suggestions from code review Co-authored-by: nabenabe0928 <47781922+nabenabe0928@users.noreply.github.com> * remove unwanted additions * Update autoPyTorch/pipeline/components/preprocessing/tabular_preprocessing/TabularColumnTransformer.py Co-authored-by: nabenabe0928 <47781922+nabenabe0928@users.noreply.github.com>
* reduce number of hyperparameters for pytorch embedding * remove todos for the preprocessing PR, and apply suggestion from code review * remove unwanted exclude in test
ravinkohli
force-pushed
the
reg_cocktails-pytorch_embedding
branch
from
October 25, 2022 15:44
cbd4d7e
to
1be80d5
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updates embedding layers to pytorch embedding.
Types of changes
Note that a Pull Request should only contain one of refactoring, new features or documentation changes.
Please separate these changes and send us individual PRs for each.
For more information on how to create a good pull request, please refer to The anatomy of a perfect pull request.
Checklist:
Description
Motivation and Context
How has this been tested?